Virtual local area network configuration for multi-chassis network element

ABSTRACT

A system, apparatus, and method for providing a plurality of internal VLANs within a networking element/node are described. Internal VLAN topologies are provisioned so that a particular VLAN(S) communicate traffic to corresponding applications. This segregation of internal traffic across a VLAN topology reduces the amount of interference between the traffic. Redundancy across the VLAN topology is provided so that traffic may be switched to another path in the event of a failure.

CROSS REFERENCE TO RELATED PATENT APPLICATIONS

This application claims priority to U.S. Provisional Application Ser.No. 60/693,895, entitled “Virtual Local Area Network (VLAN)Configuration for Multi-Chassis and High Available Network Element”,filed Jun. 24, 2005, which application is incorporated herein byreference in its entirety.

BACKGROUND

A. Technical Field

This application relates to network control management, and moreparticularly, to the use of virtual local area networks (“VLANs”) withina multi-chassis network element to manage traffic therein.

B. Background of the Invention

The importance of networking technology in today's society is wellunderstood. Communication networks have become a significant medium onwhich companies and individuals communicate. The types of informationthat are communicated on networks include voice, video, and data. Thereliability of these networks is very important in day-to-day operationsof many companies and individuals.

Network providers demand that networking elements within their networksoperate with an extremely low failure rate. A network failure event maylead to a large amount of data being lost and may significantly impactthe companies that rely on the network. These network failures may alsocause financial losses to the network providers and require significantefforts to repair.

Network providers generally require that networks, and elements therein,maintain a layer of redundancy. To that end, network elements or nodes,such as routers and switches, typically standby components that may beactivated to compensate for a failed component. In the case of such afailure, traffic may be diverted from a failed component to acorresponding standby component to allow traffic to continue to flowwithin the element. This redundancy effectively reduces the amount ofdamage caused by a failure within a network element.

Another important factor in reducing network failures is providingappropriate traffic management on the network element. This trafficmanagement includes the internal switching and processing of networktraffic from multiple ports to particular applications within theelement. This management may be complicated by having particular networkstreams having different quality of service designations which mayeffectively prioritize one stream over another. For example, datatraffic fault indication may be switched at a faster rate internallywithin the network element to ensure that data plane protection ishappening in a timely manner. Traffic management may also providerouting or switching protocols within the network element to efficientlyroute traffic between ports on the element.

Different types of traffic within a network element may interfere witheach other because of the different routing protocols/commands and thetiming of these commands relative to each other. For example, trafficinterference may occur if two different circuit packs attempt tosimultaneously communicate with other circuit packs or applications.Also, broadcast traffic coming from a communication network is typicallytransported to a management/control module in the network node but mayinadvertently be switched to another component, such as a line card,because of interfering commands at the switch.

Accordingly, what is needed is control management infrastructure withinthe internal control plane that prevents interference between circuitpacks and provides a level of internal redundancy for traffic within thenetwork element.

SUMMARY OF THE INVENTION

The present invention provides redundancy within the internal controlplane of a network element and a reduction in traffic interference bydeploying a plurality of VLANs within the network element. In oneembodiment of the invention, the plurality of VLANs are provisioned in amulti-chassis network element node in order to control traffic on thecontrol plane internal network and designed to provide redundancy withinthe element node. For example, the plurality of VLANs may provide atleast two paths on which network traffic may be communicated between aport and an application or component, such as an internal processor(s).

In another embodiment of the invention, the plurality of VLANs may bepartitioned so that certain VLANs control traffic to one application andother VLANs control traffic to another application. As a result, a VLANmay be designated to communicate a certain type of traffic to and/orfrom a particular application. This delineation among the plurality ofVLANs reduces the occurrence of traffic interference because trafficfrom different applications is more effectively isolated from each otheron the control plane of the network element.

The present invention may be implemented in various network elements,such as network switches and routers. For example, the invention may beintegrated within a network switch or aggregator within an opticallong-haul network. The plurality of VLANs may be located between abackplane and at least two processors within the network element. Insuch an environment, the invention provides internal redundancy behindthe backplane and dynamic management of traffic within the control planeof the network element.

One skilled in the art will recognize that the present invention mayalso be applied to other networking elements and environments. Otherimplementations of the present invention include provisioning VLANswithin a craft topology, a peer topology, and an optical service channeltopology.

Other objects, features, and advantages of the invention will beapparent from the drawings, and from the detailed description thatfollows below.

BRIEF DESCRIPTION OF THE DRAWINGS

Reference will be made to embodiments of the invention, examples ofwhich may be illustrated in the accompanying figures. These figures areintended to be illustrative, not limiting. Although the invention isgenerally described in the context of these embodiments, it should beunderstood that it is not intended to limit the scope of the inventionto these particular embodiments.

FIG. 1 is a general illustration of a plurality of VLANs that provideredundancy within a network element according to one embodiment of theinvention.

FIG. 2 is an illustration of a network element system having a pluralityof VLANs within its control plane according to one embodiment of theinvention.

FIG. 3 illustrates a VLAN network traffic topology according to oneembodiment of the invention.

FIG. 4 illustrates a craft VLAN topology according to one embodiment ofthe invention.

FIG. 5 illustrates a peer VLAN topology according to one embodiment ofthe invention.

FIG. 6 illustrates an optical service channel VLAN topology according toone embodiment of the invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

A system, apparatus, and method for providing a plurality of internalVLANs within a networking element/node are described. Internal VLANtopologies are provisioned so that a particular VLAN(s) communicatetraffic to corresponding applications. This segregation of internaltraffic across a VLAN topology reduces the amount of interferencebetween the traffic. Redundancy across the VLAN topology is provided sothat traffic may be switched to another path in the event of a failure.

The following description is set forth for purpose of explanation inorder to provide an understanding of the invention. However, it isapparent that one skilled in the art will recognize that embodiments ofthe present invention, some of which are described below, may beincorporated into a number of different computing systems and devices.The embodiments of the present invention may be present in hardware,software or firmware. Structures and devices shown below in blockdiagram are illustrative of exemplary embodiments of the invention andare meant to avoid obscuring the invention. Furthermore, connectionsbetween components within the figures are not intended to be limited todirect connections. Rather, data between these components may bemodified, re-formatted or otherwise changed by intermediary components.

Reference in the specification to “one embodiment”, “in one embodiment”or “an embodiment” etc. means that a particular feature, structure,characteristic, or function described in connection with the embodimentis included in at least one embodiment of the invention. The appearancesof the phrase “in one embodiment” in various places in the specificationare not necessarily all referring to the same embodiment.

A. Overview

FIG. 1 illustrates a general overview of a VLAN topology according toone embodiment of the invention. A plurality of ports or interfaces, inthis example port (0) 105, port (1) 106 and port (N) 107, on one or moretransceiver modules receive traffic that is to be internally processedwithin a network node. This processing may include switching, routing oraggregating network traffic. The plurality of ports are coupled to VLAN(A) 130 and VLAN (B) 140 that communicate the received traffic to eitheran active processor 180 or a standby processor 190. The standbyprocessor may be activated in the event that the active processor 180fails. One skilled in the art will recognize that the VLANs 130, 140 mayalso communicate traffic to other components within the network node andthat various intermediary components, such as a backplane, may belocated between the ports, VLANs, and processors.

In one embodiment of the invention, the internal physical network ispartitioned into VLAN (A) 130 which communicates traffic for a firstapplication, and VLAN (B) 140 which communicates traffic for a secondapplication. This partitioning of the physical network into VLANseffectively separates traffic associated with different applications aseach is communicated internally within a particular VLAN so thatinterference between this traffic is reduced. Traffic interference mayoccur if two different circuit packs attempt to communicate with othercircuit packs or with one of the processors 180, 190 at the same time.As a further example, broadcast traffic coming from a communicationnetwork is typically transported to a management/control module in thenetwork node but may inadvertently be switched to another component,such as a line card, because of interfering commands.

Each VLAN may also be provided a unique identifier to ensure that acorrect VLAN is being addressed to communicate a particular type oftraffic and ensure that the traffic is received at a correctdestination. In this particular example, VLAN (A) 130 may receivesignals from port (0) 105 and have a first path 120 to an activeprocessor 180 and a second path 125 to a standby processor 190. VLAN (B)140 receive signals from port (N) 107 and have a first path 133 to theactive processor 180 and a second path 135 to the standby processor 190.The use of multiple VLANs separates the traffic on the control planenetwork between ports that may be communicated to the same applicationand provides redundancy within the internal signaling infrastructure.

One skilled in the art will recognize that the above-describedprinciples may be applied to various networking environments and may beembodied in numerous topologies, some of which are described below.

B. Multi-Chassis Node Overview

FIG. 2 illustrates an exemplary multi-chassis node in which a pluralityof internal VLANs may be employed according to one embodiment of theinvention. In this particular example, the node comprises a firstchassis 210 and a second chassis 260 that operate within a network node.The first chassis 210 comprises an active processor 215, such as themanagement control module (“MCM”) processor, and a standby processor220. The first chassis also includes signal band optical multiplexer anddemultiplexer modules, such as the multiplexer/demultiplexer modules(“BMMs”) 240, for banding or debanding of optical signal groups(“OCGs”). The first chassis 210 also includes a plurality of transceivermodules/line cards, such as the illustrated digital line modules (“DLM”)235, that are connected to the processors 215, 220 by one or moreinternal switches 225, 230.

These DLMs 235 may also interface with tributary adapter modules,(“TAMs”), which provide an interface between a client's signal equipmentand a DLM. These modules are described in further detail in U.S. patentapplication Ser. No. 10/267,331, filed Oct. 8, 2001 and Ser. No.11/154,455, filed Jun. 16, 2005, which applications are incorporatedherein by their reference.

The second chassis 260 is structured in a similar manner to the firstchassis 210 in that an active processor 265 and standby processor 270are connected via internal switches 275, 280 to DLMs 290 and BMMs 295.The first chassis 210 and second chassis 260 are communicatively coupledby a first cable 245 and a second cable 250. Both the first and secondchassis 210, 260 may also have other inputs including main networkports, craft ports, auxiliary network ports, and optical service channelports.

In various embodiments of the invention, a plurality of VLANs areemployed between circuit packs in transceiver modules in a network node,which may provide various functionality in a network including being aterminal end node or and add/drop node. The communication between thetransceiver modules, and more particularly, intercommunication betweenthe modules in multiple slots in a chassis or chasses environment isaccomplished via Ethernet networking at the backplane of the modules.

In one embodiment of the invention, the first chassis 210 operates as amaster chassis and is configured by a system user. Most network elementconfigurations and activities are executed by the active node controllerCPU. However, Ethernet switches on all MCMs are used to transportEthernet/IP control plane traffic. See also pending provisional patentapplication, Ser. No. 60/695,393 entitled, “Time Synchronization forRedundant management control modules (MCMs) in Multi-chassis Networkelements (NEs),” filed Jun. 30, 2005, which is incorporated herein byits reference, and also shows the arrangement of active and standby MCMson a single chassis as shown in FIG. 2 as MCM(0) 215 and MCM(1) 220.

The Ethernet/IP control plane traffic is switched by an Ethernet switchin the management control module on each chassis 210, 260. Thecombination of the backplanes, control and timing cables, Ethernetswitches, and network element provide an internal physical control planenetwork. A network element is configured for the flow of multiple VLANs.In one embodiment, each network element has two network ports connectedto each MCM in the chassis. Because a network element is addressed witha single network IP address and the network element is managed by theactive MCM (e.g., 215, 265), the network IP address is assigned to theactive MCM, which may be either MCM(0) or MCM(1). However, the physicaltraffic may traverse into the active MCM through either the active MCMor the standby MCM depending upon which link port is connected to whichMCM (e.g., MCM(0) or MCM(1)). For example, if both network links areoperating and connected to a chassis at the same time, then the trafficwill go through the active MCM.

a) Transceiver Module VLAN Topology

FIG. 3 illustrates a network VLAN configuration topology according toone embodiment of the invention. A client network 310 is connected to arouter 320 having a plurality of ports. A first MCM (active) 340 iscoupled to the router 320 via connection 330 and a second MCM (standby)365 is coupled to the router 320 via connection 325. The configurationprovides redundant connections to both a first processor (μP) 344 on thefirst MCM 340 and a second processor 368 on the second MCM 365.

The first MCM 340 comprises a first switch including a first VLAN 360that is coupled to a first MAC (en0) 342, on the first MCM 340, which isconnected to the first processor 344. The second MCM 365 comprises asecond switch including a second VLAN 390 that is coupled to a first MAC(en0) 369, on the second MCM 365, which is connected to the secondprocessor 365.

A crosslink having a first connection 363 and a second connection 364provides redundant connections to the first and second processors 344,365. In one embodiment, this crosslink is an Ethernet crosslink having afirst connection 363 that connects the first MCM switch VLAN 360 to asecond MAC (en1) 367 on the second MCM 365 and a second connection 364that connects the second MCM switch VLAN 390 to a second MAC (en1) 346on the first MCM 340. These crosslink connections 363, 364 allow thesending and receipt of network traffic through the second (standby) MCM365 to the first processor 344. This path through the second (standby)MCM 365 may operate as a redundant path in the case of a failure.

An exemplary Ethernet switch configuration for the network is shownbelow. Each network element has two main network ports and two separateVLANs, (e.g., 360, 390) for each network port.

VLAN Slot A Switch Slot A CPU Slot B Switch Slot B CPU VLAN BNetworkPort, en0 en1 MCMProcPort, PeerMcmPort VLAN A en1 NetworkPort,en0 MCMProcPort, PeerMcmPort

In one embodiment, the network element has a single network IP address355 that defines the interface for management traffic, which may requirethat this address be switched to the active MCM when a redundancyswitching occurs.

An active MCM will be assigned the network IP address. A network port iscontinuously monitored by the MCMs 340, 365 for their link status. Atboot up, the network IP address 355 is assigned to the first MAC 342over VLAN A interface 353. This interface is directly connected to theswitch VLAN 360. In one embodiment, the switch VLAN A 360 is configuredwith CPC PROC port, peer MCM CPC port and network port which will bepart of the DCN VLAN on a first card. The switch VLAN B 390 isconfigured with CPC PROC port, peer MCM CPC port and network port whichwill be part of the DCN VLAN on the second MCM 365.

When a network link on the active MCM is detected to be down, the DCN IPaddress 355 is switched from the first MAC 342 to a second MAC 346 overto VLAN B 390. The second MAC 346 interface is connected to thesecondary or standby MCM's switch VLAN B 390 via crosslink communicationline 364 so that the IP address is stored 380 in the second MCM 365,which also is in communication with the network port. With activation ofthis switch, the traffic will start flow through the standby MCM 365.

The network IP address may be auto-reverted back to the first MAC 342over VLAN A interface 353 (i.e. active MCM 340) when the network linkstatus on the active MCM 340 is detected to be up, this will avoid theneed for monitoring the crosslink on the standby MCM 365 from the activeMCM 340 which could cause the software in the network element togenerate errors.

The VLAN topology may also be applied to auxiliary or DCN ports on thefirst chassis 210 and the second chassis 260. In one embodiment, eachnetwork element has two auxiliary ports, one port being connected to theactive MCM 340 and a second port being connected to the standby MCM 365.The auxiliary network may be configured in a similar fashion describedabove in relation to transceiver module VLAN topology but having adifferent VLAN and IP address. An exemplary switch configuration for theauxiliary or DCN network is shown below.

VLAN Slot A Switch Slot A CPU Slot B Switch Slot B CPU VLAN A AuxPort,en0 en1 MCMProcPort, PeerMcmPort VLAN B en1 AuxPort, en0 MCMProcPort,PeerMcmPort

b) Craft VLAN Topology

FIG. 4 illustrates a multiple VLAN topology within a craft environmentaccording to one embodiment of the invention. In this example, a firstactive MCM 410 comprises a craft interface 446 that is coupled to VLAN A430 which is coupled to a first MAC 427 and a first microprocessor 425.A first standby MCM 412 comprises a craft interface 447 that is coupledto VLAN B 440 which is coupled to a second MAC 435 and a secondprocessor 433. A second active MCM 414 comprises a craft interface 449coupled to VLAN C 470 which is coupled to a third MAC 475 and a thirdprocessor 480. A second standby MCM 416 comprises a craft interface 448coupled to VLAN D 450 which is coupled to a fourth MAC 455 and fourthprocessor 460.

In a multi-MCM configuration, span tree connection may run between thechassis shelves to ensure a loop tree craft VLANs topology.Inter-communication between the MCMs is provided by connections betweenthe VLANs. As shown, VLAN A 430 can communicate with VLAN B 440 via link445 and can communicate with VLAN C 470 via link 467. VLAN C 470 cancommunicate with VLAN D 450 via link 465. An optional link 468 canprovide communication between VLAN B 440 and VLAN D 450. Theseinter-communication links provide redundancy within the node and allowsa system user to access each of the MCMs from a single craft port.

In one embodiment, each chassis has two craft ports that are inputs tothe Ethernet control management system. An active node controller isconfigured with a particular craft IP address 429 and is coupled to VLANA 430, which effectively allows access to the other MCMs within thetopology via the various inter-communication links.

Various control methodologies may be employed including requiring thatall packets are switched to the active node controller MCM andterminated into the corresponding processor regardless of where thecraft PC is connected. A craft port IP address may have localsignificance only if remote network elements need to be accessed. Thisaccess may be performed through a gateway network element.

An exemplary Ethernet switch configuration for a craft network is shownbelow.

VLAN MCM Switch Node Controller CPU VLAN A CraftPort, en0 MCMProcPort,NCT1Port, NCT2Port, PeerMcmSwitchPort

c) Peer VLAN Toplogy

FIG. 5 illustrates a peer VLAN topology between transceiver modulesaccording to one embodiment of the invention. MCM(0) comprises a VLAN A510 coupled to a first MAC 515 having an associated first IP address 517and being coupled to a first processor 520. MCM(1) comprises a VLAN B540 coupled to a second MAC 545 having an associated second IP address555 and being coupled to a second processor 560.

The first and second VLANs 510, 540 allow for peer-to-peer communicationbetween the MCMs. Redundancy of this communication is provided bymultiple peer-to-peer links between the MCMs. In one embodiment of theinvention, there are three different physical paths on which Peer MCMscan communicate with each other.

A first path 533 connects a third MAC 525, having an associated IPaddress 530, on MCM(0) to VLAN B 540. A second path 535 connects afourth MAC 565, having an associated IP address 575, on MCM(1) to VLAN A510. A third path 518 connects VLAN A 510 and VLAN B 540. These paths518, 533, 535 provide peer-to-peer communication between MCM(0) andMCM(1), and redundancy if a failure should occur along one of thesepaths. Each path may be configured as a particular VLAN and IP interfaceand the peer negotiation and database replication Ethernet traffic isrunning on this particular VLAN may have a unique assigned IP address.

In one embodiment, the third path 518 communicates through an Ethernetlink between two switches associated with VLAN A 510 and VLAN B 540,with a final communication through the second MAC 545 on MCM(1). Thisthird path 518 may be under a backplane VLAN which is shared by multipletransceiver modules/cards in a network element. “Keep alive” and “Mo-Co”traffic between MCM(0) and MCM(1) may be communicated through thisbackplane VLAN. “Keep alive” traffic is a life monitoring mechanism forthe network element in which MCMs communicate messages periodically toeach other to verify that peers are operating correctly. “Mo-Co” trafficis network element configuration updates. A more detailed description ofthe backplane VLAN is provided later.

An exemplary Ethernet switch configuration for a peer network is shownbelow.

Slot A Slot A IP Slot B Slot B IP VLAN Slot A Switch CPU Address Slot BSwitch CPU Address VLAN A MCMProcPort, en0 127.4.1.122 en1 127.4.1.123PeerMcmPort VLAN B en1 127.5.1.122 MCMProcPort, en0 127.5.1.123PeerMcmPort

d) Backplane VLAN

In one embodiment of the invention, a backplane VLAN is the largest VLANwithin a network element node. It may be used for all the circuit packson multiple chasses to communicate with each other. The ports on the MCMEthernet switch, except external ports and the peer MCM port, may beassigned to this backplane VLAN.

There may be several IP subsets installed on the backplane VLAN thatallow transceiver modules, such as DLMs, to communicate with othermodules using the Ethernet switch on a local active MCM that is on thesame chassis. For example, a first subset of IP addresses is used by themodules to communicate with other modules using the switch or VLAN on afirst local module, such as the MCM(0), that is on the same chassis. Asecond subset of IP addresses may used by the modules to communicatewith other modules using the switch or VLAN on a second local module,such as the MCM(1), that is on the same chassis. Other subsets of IPaddresses may be used as floating IP addresses for an active MCM for useat anytime. Yet another subset of IP addresses may be used as floatingIP addresses for a standby MCM use at anytime. A table below shows anexemplary switch combination for the backplane VLAN.

Slot A IP Slot B IP Active IP Standby IP VLAN Ethernet Switch CPUAddress Address Address address Backplane NCT1Port, en0 127.1.x.122127.1.1.123 127.254.x.1 127.254.x.2 VLAN DLM4Port, 127.2.x.122127.3.x.122 DLM3Port, BMM1ProcPort, NCT2Port, DLM6Port, DLM5Port,BMM2ProcPort, MCMProcPort, PeerMcmSwitchPort

e) Optical Service Channel VLAN Topology

FIG. 6 illustrates an exemplary optical service channel (“OSC”) VLANtopology according to one embodiment of the invention. OSCs are opticalchannels that may be used within a network element to interconnectchasses so that data may be communicated between the chasses. In oneexample, the OSCs are a SONET OC-3c link with Ethernet framesencapsulated inside its payload.

In one embodiment of the invention, each transceiver module has an OSClink to other modules within a network element node. For example, a BMM650 may have an OSC link 645 to neighboring BMMs on other devices.Additionally, a network element may have one or more OSC interfaces onwhich it transmits and receives information.

OSC packets may be communicated between transceiver modules usingvarious methods. In one method, as illustrated in FIG. 6, an OSC VLANtopology is provided to allow OSC communication to occur as well as toenable redundant paths in case a failure occurs. OSC packets areforwarded from an OSC framer to an active node controller in an MCM. Aplurality of VLANs is provided that create at least two paths between anOSC optical link and a port for routing.

Referring to FIG. 6, a first path 635 and a second path 640 are providedbetween an OSC optical link and router 610. The first path 635 uses VLANA on the active MCM 630 to switch to traffic to the router 610 and thesecond path 640 uses VLAN B on the standby MCM 620 to switch traffic tothe router 610. Using the two paths, redundancy is created across theactive and standby MCMs.

An OSC digital framer receives OSC traffic from an optical link 645 viaa transceiver or line card module that includes a BMM 650. The OSCtraffic is forwarded to a switch in the BMM 650, which forwards the OSCtraffic to the active shelf controller switch.

The active shelf controller switch forwards traffic to the active nodecontroller switch which forwards the traffic to a processor for routing.On the node controller processor, an IP address can be defined by a userfor each OSC VLAN. IP packets may also routed to different OSCs usingsoftware on the controller processor.

The OSC traffic may be routed back to another OSC by reversing theabove-described steps and then forwarded to another network. Thistopology allows both auxiliary and network traffic to be forwardedthroughout the internal network of the network element node.

As described above, a VLAN is created on all the MCM Ethernet switchesfor each OSC. In one embodiment of the invention, a VLAN ID for each OSCis based on a formula of Shelf ID and Slot ID: OSC VLAN ID=SlotId*256+Shelf Id

MCM Switch Node MCM Switch other than Controller VLAN on Shelf X Shelf XCPU VALAN OSC1, MCMProcPort, en0 256 + X MCMProcPort, NCT1Port,NCT1Port, NCT2Port, NCT2Port, PeerMcmSwitchPort PeerMcmSwitchPort VLANOSC2, MCMProcPort, en0 512 + X MCMProcPort, NCT1Port, NCT1Port,NCT2Port, NCT2Port, PeerMcmSwitchPort PeerMcmSwitchPort

While various embodiments of the present invention have been describedabove, it should be understood that they have been presented by way ofexamples, and not limitation. It will be apparent to persons skilled inthe relevant art that various changes in form and detail may be madetherein without departing from the spirit and the scope of theinvention.

1. A network element node comprising: a plurality of network ports onwhich network traffic is received and transmitted; a switch, coupled tothe plurality of network ports, that switches the network traffic tocomponents within the network element node; a first virtual local areanetwork (“VLAN”), located on the switch, having an associated firstnetwork port within the plurality of network ports and that switches atleast a first portion of the network traffic to a first one of thecomponents; a second VLAN, located on the switch, having an associatedsecond network port within the plurality of network ports and thatswitches at least a second portion of the network traffic to a secondone of the components; a first transceiver module; a second transceivermodule, wherein the first VLAN is located on the first transceivermodule and the second VLAN is located on the second transceiver module;a first MAC, located on the first transceiver module and coupled to thefirst VLAN, on which a third portion of the network traffic is received,the first MAC being associated with a first IP address; and a secondMAC, located on the second transceiver module and coupled to the firstVLAN, on which a fourth portion of the network traffic is received, thesecond MAC being associated with a second IP address, the fourth portionof the network traffic being diverted to the second MAC in the event ofa failure, wherein the first VLAN includes a first redundant path to thesecond one of the components and the second VLAN includes a secondredundant path to the first one of the components, and wherein the firstand second IP addresses are the same address and the second IP addressis updated in the event of a failure on the first transceiver module. 2.The network element node of claim 1 wherein the first one of thecomponents is an active processor and the second one of the componentsis a standby processor.
 3. The network element node of claim 1 whereinthe network element node is a multi-chassis system.
 4. The networkelement node of claim 1 wherein the network element node operates in along-haul optical network and the switch is an Ethernet switch.
 5. Thenetwork element node of claim 1 wherein the first and second VLANsoperate in transceiver module VLAN topology.
 6. A network elementcomprising: a plurality of transceiver modules, within a network elementnode, that transmit and receive network traffic; a first craft port, ona first transceiver module within the plurality of transceiver modules,on which a craft personal computer may interface and communicate withthe network element node; a first VLAN, located on a switch within thefirst transceiver module, that receives information from the first craftport; a second VLAN, located on a second transceiver module within theplurality of transceiver modules, that receives the information from thefirst VLAN to enable a user to communicate with the second transceivermodule; a third VLAN, located on a third transceiver module within theplurality of transceiver modules, that receives the information from thefirst VLAN to enable a user to communicate with the third transceivermodule; a first MAC, located on the first transceiver module and coupledto the first VLAN, on which a third portion of the network traffic isreceived, the first MAC being associated with a first IP address; and asecond MAC, located on the second transceiver module and coupled to thefirst VLAN, on which a fourth portion of the network traffic isreceived, the second MAC being associated with a second IP address, thefourth portion of the network traffic being diverted to the second MACin the event of a failure, wherein the first and second IP addresses arethe same address and the second IP address is updated in the event of afailure on the first transceiver module.
 7. The network element of claim6 wherein the first VLAN, the second VLAN and third VLAN communicateusing Ethernet inter-communication connections.
 8. A network elementcomprising: a first transceiver module; a second transceiver module; afirst VLAN, located on a first switch within the first transceivermodule, that receives network traffic from a client network; a secondVLAN, located on a second switch within the second transceiver module,that receives network traffic from the client network; a first MAC,located on the first transceiver module and having an associated firstIP address, that communicates with the second VLAN via a firstpeer-to-peer link; and a second MAC, located on the second transceivermodule and having an associated second IP address, that communicateswith the first VLAN via a second peer-to-peer link; wherein the firstand second IP addresses are the same address and the second IP addressis updated in the event of a failure on the first transceiver module. 9.The network element of claim 8 further comprising a third peer-to-peerlink that couples the first VLAN to the second VLAN.
 10. The networkelement of claim 9 wherein the third peer-to-peer link is under abackplane VLAN which is shared by the first and second transceivermodules.
 11. The network element of claim 10 wherein the backplane VLANis associated with a plurality of IP subset addresses that allowcommunication between the first and second transceiver modules.
 12. Anetwork element comprising: a banding/debanding module that receives ortransmits optical signal groups; a first transceiver module including afirst VLAN, the first transceiver module being coupled to thebanding/debanding module, the first transceiver module receives andswitches, with the first VLAN, first traffic carried by first ones ofthe optical signal groups; a second transceiver module including asecond VLAN, the second transceiver module being coupled to the firsttransceiver module, the second transceiver module receives and switches,with the second VLAN, second traffic carried by second ones of theoptical signal groups; a first MAC, located on the first transceivermodule and coupled to the first VLAN, on which a third portion of thenetwork traffic is received, the first MAC being associated with a firstIP address; and a second MAC, located on the second transceiver moduleand coupled to the first VLAN, on which a fourth portion of the networktraffic is received, the second MAC being associated with a second IPaddress, the fourth portion of the network traffic being diverted to thesecond MAC in the event of a failure, wherein the first and second IPaddresses are the same address and the second IP address is updated inthe event of a failure on the first transceiver module.
 13. A method forproviding redundancy and network traffic segregation within amulti-chassis network node, the method comprising: receiving a firstnetwork stream on a first port; receiving a second network stream on asecond port; switching the first network stream on a first VLAN to anactive component within the multi-chassis network node; switching thesecond network stream on a second VLAN to the active component withinthe multi-chassis network node; maintaining a first connection of afirst redundant path in the first VLAN to a standby component within themulti-chassis network node; and maintaining a second connection of asecond redundant path in the second VLAN to the standby component withinthe multi-chassis node, wherein each of a plurality of MACs has acorresponding one of a plurality of IP addresses that allow theswitching of the first network stream and the switching of the secondnetwork stream, first and second ones of the plurality of IP addressesbeing the same address and the second one of the plurality of IPaddresses is updated in the event of a failure on the first transceivermodule.
 14. The method of claim 13 wherein the active component is anactive processor and the standby component is a standby processor. 15.The method of claim 13 wherein the first port is a craft interface portthat allows a craft PC to communicate with a first chassis within themulti-chassis network node.
 16. The method of claim 15 wherein theactive component and the standby component are located on a secondchassis within the multi-chassis network node.
 17. The method of claim13 wherein a communication between the first VLAN and the second VLANoccurs under a backplane VLAN associated with the multi-chassis networknode.